Skip to content

Conversation

altendky
Copy link
Contributor

No description provided.

Comment on lines +79 to +87
all:
uses: ./.github/workflows/all.yml
if: always()
needs:
- macos
- ubuntu
- windows
with:
needs: ${{ toJSON(needs) }}

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey, I noticed you're reinventing the wheel here :)

I've got this https://github.com/re-actors/alls-green implemented a while back. Inspired by PyCA and some other research.

Suggested change
all:
uses: ./.github/workflows/all.yml
if: always()
needs:
- macos
- ubuntu
- windows
with:
needs: ${{ toJSON(needs) }}
all: # This job does nothing and is only used for the branch protection
if: always()
needs:
- macos
- ubuntu
- windows
runs-on: ubuntu-latest
steps:
- name: Decide whether the needed jobs succeeded or failed
uses: re-actors/alls-green@release/v1
with:
jobs: ${{ toJSON(needs) }}

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't know about reinventing... pytest-dev/pytest-twisted@4c75379 :] but yes, thanks for the heads up on your action. I noticed it over in the towncrier comments as well. I'm glad to see this practice has some traction.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, we've faced this problem in aiohttp where automerge would merge broken PRs and I've accidentally seen the solution in PyCA/cryptography, then gone ahead and generalized it a bit :)

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As for "one check for branch protection" idea, it's ancient. Coming from CIs like Zuul and Bors.

@github-actions github-actions bot added the merge_conflict Branch has conflicts that prevent merge to main label Sep 16, 2022
@github-actions
Copy link
Contributor

This pull request has conflicts, please resolve those before we can evaluate the pull request.

@altendky
Copy link
Contributor Author

altendky commented Sep 3, 2025

closing in favor of #20026 for logistical reasons. thanks 🇺🇦

@altendky altendky closed this Sep 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
merge_conflict Branch has conflicts that prevent merge to main
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants